|
Spock is a Java testing framework capable of handling the full life cycle of a software application. It was initially created in 2008 by Peter Niederwieser, a software engineer with GradleWare. A second Spock committer is Luke Daley (also with Gradleware) who is also the creator of the popular Geb functional testing framework. Spock is a new entry in the test framework arena and currently challenges the undisputed king - JUnit - armed with its fresh ideas against the legacy techniques of the past. == Main features == Main Features of Spock: *Enterprise ready - Spock can be easily integrated with the popular build systems (Maven and Gradle), runs as part of a build process, and produces reports of automated test runs. Spock can be used to test backend code, web pages, http services, and more. *Comprehensive - It has built-in mocking and stubbing capabilities allowing you to decide on the breadth of the testing context. Spock can test a single class, a code module, or a whole application context with ease. It is possible to perform end-to-end testing with Spock or isolate one class/method for testing needs without any external libraries. *Familiar/Compatible - Spock runs on top of the JUnit runner which already enjoys mature support among tools and development environments. Spock tests are run in the same way as JUnit tests. You can even mix the two in the same project, and get reports on test failures, or code coverage in a similar way to JUnit. Run your tests in parallel or in a serial way, Spock does not care because it is fully compatible with existing JUnit tools. *Inspired - Spock is relatively new and does not carry any legacy burden. It is designed from scratch but takes the best features of existing testing libraries. For example, Spock embraces the given-when-then structure of JBehave but also discards the cumbersome record/replay code of older Mocking frameworks. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Spock (testing framework)」の詳細全文を読む スポンサード リンク
|